Skip to content

feat: support Atlas Cloud environment configuration - #265

Open
binyangzhu000-sudo wants to merge 3 commits into
lessweb:mainfrom
binyangzhu000-sudo:feat/atlascloud-provider
Open

feat: support Atlas Cloud environment configuration#265
binyangzhu000-sudo wants to merge 3 commits into
lessweb:mainfrom
binyangzhu000-sudo:feat/atlascloud-provider

Conversation

@binyangzhu000-sudo

Copy link
Copy Markdown

Summary

  • use ATLASCLOUD_API_KEY as an opt-in credential when no explicit API_KEY is configured
  • select the Atlas Cloud OpenAI-compatible base URL and namespaced DeepSeek V4 model by default
  • preserve explicit user, project, and DEEPCODE_* settings precedence
  • recognize the namespaced model for thinking-mode and multimodal capability defaults

Validation

  • npm run generate && npm run check
  • npm test (596 passed, 1 skipped)
  • Atlas Cloud model discovery through createOpenAIClient() (123 models; default model present)
  • Atlas Cloud chat completion through createOpenAIClient() (non-empty response)
  • git diff --check

No README, public documentation, logo, dependency, or lockfile changes.

binyangzhu000-sudo and others added 2 commits July 29, 2026 23:27
Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Resolved the merge conflict with current main in follow-up commit 7084a7b9.

The resolution preserves both the Atlas Cloud settings tests and the new upstream context-window tests. The online PR diff remains limited to the original four core files.

Validation:

  • Focused settings tests: 35 passed, 0 failed
  • Core test suite: 281 passed, 1 skipped, 0 failed
  • All workspace typechecks passed
  • ESLint, Prettier, conflict-marker, and diff-scope checks passed

The exact-head CI workflow currently shows action_required, so it needs maintainer approval to execute for this fork PR.

Three conflicts, all from upstream refactors this branch overlapped:

- model-capabilities.ts: upstream replaced the NON_MULTIMODAL_MODELS set
  with supportsMultimodal(model, mode), inferring from "-vision". Took the
  new mechanism and dropped this branch's list, having first checked it has
  no remaining consumers. The Atlas model id stays in DEEPSEEK_V4_MODELS,
  which still drives the thinking-mode default.
- index.ts: both sides added exports; kept both.
- settings.ts: upstream hoisted baseURL into a local. Folded the Atlas
  default into that local instead of the return site, so baseURL now mirrors
  how model already handles useAtlasCloudDefaults.

Signed-off-by: binyangzhu000-sudo <binyangzhu000@gmail.com>
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Synced with main (79 commits). Three conflicts, all where this branch overlapped an upstream refactor:

  • model-capabilities.ts — you replaced the NON_MULTIMODAL_MODELS set with supportsMultimodal(model, mode) inferring from -vision. Took the new mechanism and dropped this branch's list rather than reinstating it; I checked first that it has no remaining consumers anywhere in packages/. The Atlas model id stays in DEEPSEEK_V4_MODELS, which still drives the thinking-mode default, and it correctly resolves to non-multimodal under the new rule.
  • index.ts — both sides added exports; kept both.
  • settings.ts — you hoisted baseURL into a local. I folded the Atlas default into that local rather than patching the return site, so baseURL now mirrors how model already handles useAtlasCloudDefaults:
const baseURL =
  trimString(env.BASE_URL) ||
  (useAtlasCloudDefaults ? ATLASCLOUD_BASE_URL : "") ||
  defaults.baseURL;

Verificationnpm run typecheck clean across both workspaces (@vegamo/deepcode-core, deepcode-vscode). Diff against current main is +57/-3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant